pp108 : Scheduler Service Interface

Scheduler Service Interface
This topic describes the fields on the Scheduler Service interface.

The following tables describe the fields on the Scheduler tab of the Scheduling service container.

Table 1. Fields on the Scheduler Service tab.

Field

Action

Select Database Configuration

  • To create a Database Configuration - Select the New Database Configuration option from the drop-down list and provide the required information in the dialog box that appears.
  • To continue with an existing Database Configuration - Select the required database configuration from the drop-down list. The associated fields are automatically filled.

Advanced Options

Expand the group box and provide the necessary details.

Setting Cursor Cache Size to a high value would cause high memory consumption. Based on the application usage, administrator has to set an optimal value. This is also applicable to the Query Cache size.
For example: The optimal cursor cache size can be between 50 - 100, subjective to the application usage.

Scheduler Engine tab

When the schedule service container is stopped due to network failure or stopped manually, the schedule instances during the downtime are termed as Missed Schedules.
For example: Let us assume that a task is scheduled to be triggered hourly at 15th, 30th, 45th, and 59th minute, that is 4 times in an hour. If the Scheduling service container is stopped on the 10th minute of the hour and is restarted on the 40th minute, the 15th and 30th minute schedules are not triggered. So, in such situations, an Administrator can configure to trigger none/one/all of the missed schedules by selecting one of the following options in the Scheduler Engine tab.

Table 2. Fields on the Scheduler Engine tab

Field

Action

Trigger none of the schedule instances on start-up which are missed during downtime

Select this option, if you do not want any missed schedules to be triggered upon restarting the Scheduling service container.

Trigger one schedule instance per schedule on start-up which are missed during downtime

Select this option, if you want only one instance of the missed schedules to be triggered upon restarting the Scheduling service container. As per the example, the schedule will be triggered once at the 40th minute and the remaining schedules will follow the plan.

Trigger all the schedule instances per schedule on start-up which are missed during downtime

Select this option, if you want all the instances of the missed schedules to be triggered upon restarting the Scheduling service container. As per the example, the 15th and 30th minute schedules will be triggered at the 40th minute (that is, two times) and the remaining schedules follow the plan.